Inspection - Materials Management

Inspection - Materials Management

• Description
• Functionality
• Related topics
• Technical documentation

Description

This app is used to control data relating to materials management in general. For this purpose, there are inspection runs that are intended to help maintain or achieve a clean and consistent data stock. Various inspection runs from the entire system are compiled in this app. Next to the execution button on the screen, there is a short description of the inspection run.

There are local inspection runs that are executed in the inspection results window and inspection runs that call up other apps and are started or evaluated there.

To get a better overview, the inspection window is divided into different sub-windows. The sub-windows are then also divided into sub-groups with more precise specification of the topic.

Functionality

• Selection window
• Results window
• Parts Environment Test Window

Selection window

The various inspection runs can be called up from this window.

Some test runs offer the possibility to limit the search results to "only bearing parts". The following description can be used as a definition for "bearing part":

• Part is per staging type
  • stocked
  • Remaining quantity
  • Hand bearing part
• or the part has a stock

Menu

Menu item	Description
Edit	-
: Set default settings
Open results window	Call up results window

Implemented inspection runs (fields and buttons)

Field	Description
Sub-tribe
: number of parts	-
: : Display number of parts	Selection shows number of parts
: Parts registration	-
: : partial registration	This test searches for variant parts that cannot be found in the part master. This condition may have arisen due to technical changes in the system. These parts are then made findable in the parts master and displayed in the results list.
: Units	-
: : conversion tables	Parts are searched for which have an inconsistent unit table. A detailed description of what inconsistent unit tables are can be found here.
: : Posted quantities	Test searches for parts where quantities are posted in MRP or warehouse accounts that do not match the part's own unit table or cannot be converted to the standard unit.
: Parts organisation	-
: : parts environment	Parts environment test
: : No deployment type	Test searches for parts for which it has not yet been determined whether the part should always be in stock or ordered when required. The possible setting options can be found here.
: : No logistics KZ	Test searches for parts for which it has not yet been determined whether they are to be purchased or manufactured in-house. The result is output in the window.
: : No part usage	All parts are searched depending on whether they are either not used in any master BOMs or have never appeared in an exploded production BOM. The result is displayed in the window.
: : Duplicate lower parts	Test searches for sub-parts that exist several times in the variant part in the attribute specification.
: Part validity	-
: : Invalid parts	Search invalid parts (window)
: : Invalid parts in parts lists	Find invalid parts in master BOMs (window)
: : Valid storage bins	Invalid parts with valid storage bins (window).
Parts master II
: Attributes	-
: : Incomplete attributes	Check all subparts/sales roles/assembly set items of variant parts for complete attributes.
: : Incomplete sales set attributes	Test such sales set items with missing attributes against the sales role.
: : Attributes with value specifications	Test searches for variant parts that have attributes with value specifications
: : parts without weight	Test searches for parts without weight. First it is searched whether the unit table of a part contains a weight conversion; if this is not the case, the part is searched for an attribute with the name "weight". If both fail, the part is output as a part without weight. With the specification "Only parts with sales roles" only those parts are checked that have any sales role (sales item, spare part, special sales part, etc.). This can be used, for example, to ensure that sales items in a delivery note always have a weight. Service items (CX_SERVICE) are excluded from this test.
: : Deviation attributes	Test looks for sub-parts with deviation of attribute values between sub-part and roll.
: item numbers	-
: : commodity codes used	Test collects all specified commodity codes from the part master. Each commodity code is output only once. If the identifier "per part class" is set, each combination of part class and commodity code is output - also only once.
: : Missing commodity codes	Test checks all commodity numbers specified in the part master against the commodity number register of the Combined Nomenclature. Parts without commodity numbers ("Skip parts without commodity numbers" switch off) and all parts individually ("Output missing commodity number only once" switch off) can also be output. If no commodity numbers have been entered in the register of the Combined Nomenclature yet, you can use this run to have all commodity numbers used in the parts master - and thus missing in the register - output as an Excel file. This file can then be read in again in the Combined Nomenclature module under the Maintenance menu item and supplemented there with the data from the SOVA master file.
Part rolls
: Production parts	-
: : No production roll	Production parts defined by logistics indicator are searched for, for which no production role (production data) has been created yet. All required data such as manufacturer costs, material costs, replenishment times and so on are stored in the production role.
: : Several production roles	Production parts defined by logistics indicator are searched for, for which more than one production role has been created.
: : No parts list	Test searches for production parts that do not have a bill of material or a routing.
: : No preliminary costing	Test searches for production parts that have no preliminary costing since specified date.
: : Long lead time	Test searches for production parts that have a longer lead time than the value from the input field or an invalid value.
: Order parts	-
: : No order part roll	Order parts defined by logistics indicator are searched for, for which no order article (purchasing data) has been created yet. Each order part should have an order article role in which the procurement data such as replenishment time (delivery periods), prices, supplier agreements (special prices with some suppliers...) are defined.
: Multiple purchase order item roles	Order parts defined by logistics indicator are searched for, for which more than one order article role has been created.
: : No A-supplier	Order item roles are searched for, for which one or more supplier agreements have been defined, but not one supplier has been selected as the main supplier.
: : No purchasing area	Test searches for purchase order items that are not assigned to a purchasing area.
: : Search for order items	Test searches for purchase order items for which the lot size differs between the standard procurement data and the A-supplier.
: sales item	-
: : VK article tests	Open sales item window with further test options. (window)
: Spare parts	-
: : Spare parts tests	Open spare parts test window with further test options. (window)
: validity	-
: : Valid roles	Test searches valid roles from invalid parts.
Part cost
: roll prices	-
: : No standard price	Test searches for parts whose main role, defined according to the logistics indicator, does not contain a standard price or this is zero.
: : Wrong price table	Test searches for order item roles whose price table does not provide a price at the standard order quantity. This is an organisational error that should be avoided. For standard calculations where no current quantity is available, the price is determined using the standard order quantity. If this price is then zero because there is no table entry for this quantity, this calculation can only be included in the evaluation with the value 0EUR. The output takes place in the extra window.
: : Wrong price unit	Test searches for order parts and sales parts where the price units do not match the standard order quantity.
: : Wrong cost table	Test searches for production parts where the cost tables do not match the lot size.
: : Incorrect overhead costs	Test searches for production parts where the overhead costs are missing or have been overwritten by another price.
: : Standard quantity is zero	Test searches for order item and production roles that contain a price table but whose standard quantity is zero. In this case, the most expensive price would always be determined when determining the standard price, although this part is always ordered 2000 pieces at a time and therefore a much lower price would result. For parts without a price table, this does not matter because the price is always the same for each quantity.
: : Bottom part without price	Cockpit run for subparts that share the order article role of the variant part and for whose characteristics there is no price, or a price that is incompatible with the standard unit of the part. The test run can be called up from the part master for all selected parts or from the cockpit for all subparts of all valid variant parts.
: Update standard price order item	-
: : Update standard price	- Updating the standard price in the order item with the current A supplier or just checking how the standard price would change or if one is available at all. - The search can be limited to parts that have a storage location. - The following cases are distinguished : Case Message text Description 01 No supplier data There is no A or B supplier in the ordering role of the part or no supplier can be found via the movement monitor. 02 No price on supplier data There is no price in the supplier data 03 Part has no standard order quantity Order item has no order quantity 04 Old price conditional table, new price simple. Price is transferred to standard price 05 Old price simple, new price conditional table Table is transferred to standard price 06 Old price table, new price table - different columns Table is transferred to standard price 07 Old price table, new price table - same columns Table is transferred to standard price 08 Old price single, new price single Price is transferred to standard price 09 No old price 10 New price would be zero! No price is transferred to the standard price 11 Old price simple, new price table, no price for lot size No price is transferred to the standard price 12 Old price single, new price table, price found for lot size! Price for lot size is transferred to standard price 13 Old price simple, new price table, no quantity-dependent price table! No price is transferred to the standard price 14 Old price table, new price table, old table is not a quantity-based price table! No price is transferred to the standard price 15 Old price table, new price table, quantity-dependent price table, entry for lot size available, take over as entry in existing price table! Price for the solution size is entered in the existing table. 16 Old price table, new price table, quantity-dependent price table, NO entry for lot size available, NO price transfer! No price is taken over in the standard price 17 No new price available A CX_PRICE_DISCOUNT object was found, but no price could be determined. Options: Only parts without invalidating prices If a new price (current price becomes invalid) has already been defined for a part, then these parts are not to be considered by this run.
Stock
: bearing	-
: : Negative stock	Test looks for warehouses that currently have negative stock.
: : Inval. Stock	Test searches for invalid warehouses that still have a positive or negative stock.
: : Stock without inventory	Test searches for storage bins for which no inventory has been taken since the date to be entered. As an option, all invalid warehouses can be ignored during the test. (Info: Only storage bins without stock can be set to invalid).
: Storage bins	-
: : Stockyard numbers control	Search run checks all storage bins for multiple assignment of the number within a bin or if the storage bin has no number. The storage bins found are displayed in the results window.
: : Empty storage bin number	This reorg sets empty bin numbers to the number of the bin if the number of the bin has not yet been assigned to another bin in the bin and the bin does not have multiple bins without a name. After completion, the processed objects are displayed in the result window. It is recommended to start the "Stockyard number check" run before reorging. If the check mark "Also correct afterwards" is not set, only found objects are displayed. When the window is opened, the tick is set.
: Specifications
: : Specifications control	Specifications of variant parts can, should only be stored in project warehouses, as no value and cost determination can be made for them. With this test you can search for normal stocks of specifications. The result is displayed in the stock list and can be checked there.
Stock account
: Stock account registration	-
: : warehouse account registration	Test searches for parts whose stock accounts (CX_STOCK_ACCOUNT objects) are not registered in the REP collection and registers them there.
: Main storage bin	-
: : No occupancy in main storage bin	Test searches for parts whose main storage bin has never been moved. Either the part then actually has another main storage bin, or it has actually never been moved.
: : No movement at all.	Test searches for bearing parts that have never been moved.
: : Invalid main storage location	Test searches for parts that have an invalid main storage bin. This inevitably occurs when a warehouse is invalidated but its storage bins are still entered as the main storage bin in various parts.
: Average price on warehouse account	-
: : check average price	Stocked parts are searched for that do not have an average price on the stock account or the average price is zero. In addition, average prices can be checked that have a greater deviation from the standard roll price plus or minus the recorded percentage. The option can be used to enter the price from the standard procurement roll as the average price for all parts found. If the standard roll price is zero, it is not adopted and the parts are marked in the list.
: Stock	-
: : Stock ung. Parts	Test searches for invalid parts that still have stock.
: : Stock ung. Stock pl.	Test searches for parts that have an invalid storage bin with stock.
: staging type	-
: : Transferred storage parts	Test searches for MRP parts that still have part requisition items in material withdrawal status.
: : Missing min./max. quantities	Test searches for stock-managed parts without min./max. quantities.
: : Defined min./max. quantities	Test searches for non-stocked parts with defined min./max. quantities
Stock statistics
: stock statistics for current statistics period	For all tests described here, the following applies: The tests are only executed if the option"Redetermine results" has been selected. If the option"show last results" has been selected, as is the default, only the results of the last test are also displayed! In addition, the check is only carried out for the current statistics period. If another statistics period is to be tested, it is recommended to only display the current result of the current month, then close the results window, then set the desired month in the warehouse statistics and select the test to be carried out via the "Test" menu. Please bear in mind that these tests may take some time depending on the amount of data. For this reason it is possible to display the last results again within one second by pressing a button.
: : No price	Test searches for receipts that were posted within the current statistics period and have no price, or the price is zero.
: : Negative closing balance	Test searches for statistics of the current statistics period (part/warehouse) that have negative ending balances.
: : Value without quantity	Test searches for statistics of the current statistics period that have an ending stock of zero but have an ending value greater than or less than zero. These cases are automatically corrected at the end of the month. The test is therefore used for the evaluation of statistics periods that were closed before 2003, when these cases were not automatically corrected.
: : Outflow of zero quantity	Since it is expressly desired and wanted to post an issue even from a zero stock in a warehouse (e.g. the goods receipt has not yet been posted because the corresponding employee is ill), there is the possibility of bringing these "twisted" goods receipts and issues back into the correct order, if one can find out where this is the case. This is exactly what this check is for. A new date for the goods receipt can then be entered in the results list, so that it then lies before the goods withdrawal in terms of time. This is also important for ensuring that the moving average price is calculated correctly on the statistical and warehouse accounts.
: : average price	Test looks for parts where the average price in the logistics account is not equal to the average unit value of the last warehouse statistics.
: Stock statistics in general	-
: : Interrupted chain	If the month-end closing for a part is not done within a current year, for example because the checks failed, but the next month was closed again properly, it can happen that the last month is worked with wrong initial values. For these parts, all month-end closings since the "gap" up to the last closed month must be repeated. This test run has been written to detect these parts.
: Correct differences storage location accounts-. Warehouse statistics	(Further information)
: : Broken chain	Stock statistics are searched for parts that were either not completed, or were still modified after completion. All monthly closures displayed in this test must be repeated, then proceed with steps 2 to 4.
: : Differences storage bin accounts	In all storage bins for all parts, go back to the last inventory, take the counted quantity as the start quantity and add - or deduct - all document quantities accrued from the inventory posting. The final total from this calculation is then compared with the actual final stock stored in the storage bin account. If there are differences, it is possible to correct individual entries or all of them.
: : Differences warehouse accounts	For each warehouse account, a total is formed from all storage bin accounts and compared with the total quantity currently on the warehouse account.
: : Differences warehouse statistics	The most recently posted warehouse statistics are determined from all parts and their current quantity is compared with the total of all storage bin accounts of this warehouse. If there are differences, these parts are listed. The possibility of correction is blocked with this function, as it is executed without document and traceability.Thefunction "Set initial values with inventory"should be used for the correction of warehouse statistics. should be used. This function can be activated by a trained AppswareHouse consultant. It should be borne in mind that the correction is realised with virtual inflow or outflow quantities, which can subsequently no longer be traced due to the posted documents. This correction should therefore only be used as an extreme emergency step when all other possible causes of error have been excluded.
: : Last 2 Execute	The last 2 runs are executed one after the other.
Dispatch account
: Dispo account registration	-
: : Dispatch account registration	Test searches for parts whose dispo accounts (CX_DISPO_ACCOUNT objects) are not registered in the REP collection and registers them there.
: Dispo account entries	-
: : total dispo entries	The number of all documents posted in the MRP accounts of parts is determined. This test serves to get a feeling of whether work is being done sensibly. If there are always a lot of unprocessed provisions, the number of entries slowly increases. Likewise, unfinished orders that never go to the supplier or have gone, that were simply forgotten to cancel, etc.
: : Search parts	You are asked to enter a number. Then parts are searched for which the same number - or more - of MRP entries are booked.
: : Search for receipts	You are prompted to enter a date. Then all parts dispo accounts are searched for documents that are at least as old as the date entered. This makes it possible to find old entries that are erroneously still registered in the dispo account. For example, this is the case if a goods withdrawal has not yet been posted for a production order. This withdrawal then remains in the MRP account. In addition, an option is offered that simply removes erroneously stuck documents from the MRP account. An obviously incorrect document is, for example, a goods withdrawal that is older than the date entered and whose order item predecessor was delivered a long time ago. These documents are NOT cancelled, they are simply removed from the MRP account WITHOUT changing the total stock quantities. The posted quantities that this document has set high therefore remain at the high value. This is necessary because sometimes an inventory or stock correction has already taken place which has already corrected the stock quantity!
: : Post out obviously wrong documents
: Dispo account quantities	-
: : Negative goods receipt quantity	This finds MRP accounts on which a negative goods receipt quantity is posted. This can happen if the goods receipt is processed incorrectly (e.g. staged and then wantonly still stored). The individual cases that cause this circumstance have already been resolved.
: Worklist	-
: : Finished, registered AFO	Check the worklist against the work sequences in the work centres' MRP account. Work sequences that have already been registered as completed via a PDC booking or where the preceding goods (production or internal order) have already been cancelled or registered as completed are listed in an extra window. If the checkbox "correct" is selected, the items are deleted directly from the MRP accounts of the workstations.
Transaction data
: Order system	-
: : parts different	Test searches for order items that have a purchase order for a different part as a successor, but this is not marked as an additional purchase order, contract for work or alternative part. Due to such an incorrect order, the order item cannot be provided and remains registered in the MRP account with its open quantity.
: : Check billing values	Test searches for orders whose calculated value deviates very strongly from the actual order value (too much or too little calculated, although order is in the status "completely calculated").
: : Missing dispo status	Test searches for order items that have a bill of materials but no MRP status.
: warehouse	-
: : Negative goods receipts	Test searches for goods receipts that contain a negative quantity. Such goods receipts should only be used if an incorrect quantity of goods was mistakenly stored on an old document that can no longer be changed. To avoid having to post a withdrawal, which is then also evaluated in the warehouse statistics, you can post a negative goods receipt in these cases, which only reduces the goods receipt value by the value entered, i.e. does not increase the goods issue value (otherwise it would count as turnover). Unfortunately, the possibility of a negative goods receipt can be misused to achieve a better result in an inventory. Then the difference quantity is simply booked out via a negative goods receipt and the official deviation in the inventory is already 0. This test run was created to detect these cases of cheating.
: : No cost causer	Test searches for warehouse documents that have neither a preceding document nor a cost centre as the cost originator. These documents cannot then be assigned to a cost centre or cost object.
: : Unposted warehouse receipts	Test searches for stock-in, stock-out and stock-transfer documents that were created in a statistics period and not posted until the statistics period was closed. These errors also result in a less accurate final statistics result.
: Manufacturing	-
: : How often manufactured?	The text field "Period" is used to specify a period in which it is then checked for all production parts how often they occurred in a production order. This test produces a list of results in which the number of times each part was produced is shown in a column. This number does not represent the quantity produced, but the actual number of production orders. This list can then be used to evaluate for which production parts it would be worthwhile to switch to "stock control". By switching to stock management, much larger stock order quantities could be produced in one go, which would then only need to be withdrawn for the respective orders. This also saves time later for the overall order.
: Parts usage
: : part usage	Currently no longer supported: see part usage module. Parts use or parts usage in the last e.g. 12 and 36 months (2 entries can be made). All stock movements (without stock transfers, inventories), direct dispatch, production orders, goods receipts and incoming invoices are taken into account.
: : Not used since/used in period	Test searches for parts that have not been used since a period of time. If the number of parts found reaches the limit, the search process is aborted! The complementary search finds parts that have been used in the specified period. In principle, all parts are used for this evaluation; however, JIT parts, Kanban parts and manual stock parts without stock management are not evaluated. The use of the part in a stock transfer, in a production bill of materials, a sales order, an internal order (no stock orders!), a parts disposition with level > 0, an advance requirement or a goods receipt is considered as "use". Related to this are the modules Part Usage (intended for use by engineering), Part Usage (intended for use by service/sales) and Part Consumption (intended for use by logistics).
Provision
Open stock reservations	-
: : Open manufacturing sub-items.	Test looks for open stock reservations that should be withdrawn for production order items that have already been staged and probably have been withdrawn, just not booked out in the system by a goods withdrawal document.
: : Open completed preliminary reservations.	Test looks for open stock reservations that should have been withdrawn for already completed preliminary requirements and probably have been withdrawn, but not posted in the system by a goods withdrawal document.
: : Open in. Stock req.	Test looks for open stock reservations that should have been withdrawn for stock order items that have already been put away and probably have been withdrawn, but not posted in the system by a goods withdrawal document.
: : Open gel. Sales order	Test looks for open stock reservations that should have been withdrawn for sales order items that have already been delivered and probably have been withdrawn, but have not been posted in the system by a goods withdrawal document.
: Open provisions	-
: : Open deployments	Test searches for all open, non-provided parts requisition items for provided production order items (purchase requisition, stock reservation, production order, ...).
: Provisions - goods receipts	-
: : Placed in stock and readied. WE	Test searches for goods receipts that were incorrectly staged but nevertheless put away.
: Staging - Superfluous data	-
: : Superfluous parts list	Test searches for order items completely withdrawn from stock that have an unfinished bill of materials.
: Open staging - exchange part	-
: : Multiple withdrawals	Test searches for order items that have been taken multiple times by their exchange part.
Manufacturing
: parts lists	-
: : Display number of parts lists	In this inspection run, the number of valid and the number of invalid BOMs are output. It is also determined how many BOMs have variant items or refer to variant parts. The box "with count of production levels" is used to additionally determine and output the maximum production level of the BOMs.
: : Same BOMs	In this inspection run, identical BOMs are searched for.
: : Bills of material without part allocation	With this inspection run, BOMs are output that are not assigned to any production part
: : Part states in parts lists	Parts can be assigned to any number of classification terms. Among other things, such classification terms can also describe the status of parts, such as "In process", "Released" "Locked", etc.. With this inspection run it is possible to check in parts lists, e.g. in the status "Released", whether all parts - which occur within the parts lists - also have the status "Released". It is thus checked to what extent a status (part status) of a part corresponds to the status (part status) of all parts in its parts list.
: routings	-
: : Display number of routings	In this inspection run, the number of valid, invalid BOMs is output. It is also determined how many BOMs have variant items at all or refer to variant parts. The box "with count multiple use" is used to count the routings that are assigned to several production parts at the same time, i.e. are used several times.
: : Same/similar routings	In this inspection run, identical or similar routings are searched for. Routings are the same if all work sequences and their times are identical. Similar routings can also be determined by specifying setup and piece time patterns. A time grid of e.g. 5min means that all time specifications within the grids 0-5min, 5.01-10min are always regarded as the same.
: Constructive assembly
: : Disabled assemblies	Test searches BOM item where constructive assemblies are not used as such.
: : Activated assemblies	Test searches BOM item that is not a constructive assembly but is used as such.
: : Resolved assemblies	Test searches resolved BOM item with constructive assemblies and displays the successor.
: : Deactivated part identifier	Test searches resolved BOM item where constructive assemblies are not identified as such even though the part holds the identifier.
Technical administration
: Dispatch account	-
: : Stopped o. revers. Entries	Test looks for MRP accounts in which stopped or cancelled entries are recorded. Stopped entries are normal, but cancelled entries should no longer appear.
: : No open quantity	Test looks for entries in MRP accounts that have an open quantity of zero. Except for goods receipts that are still posted due to insufficient QA, this means that the receipts have remained in due to an error.
: : Deleted entries	Test searches for MRP accounts containing entries that have been deleted and are only shown with a red X in the MRP account without quantities and document details.
	: : Check MRP balance
Test compares the MRP stock with the quantities in MRP warehouses.	: balance differences
-	: : search balance differences
Test checks whether the quantities posted to the MRP account, such as "sales order quantity" or "production order quantity", match the total of all visible documents in the MRP account. If there is a difference, the difference is described in red in the lower area when the MRP account is opened. All MRP accounts that show such a difference are collected and displayed in this check run, but not yet corrected!	: : Balance diff. + comparison
All balance differences are compiled as in the point described above. The result is compared with the last compilation of the balance differences and only the new parts added since then are displayed.	: : Compare last result only.
No recompilation of the balance differences takes place, only the last two results are compared and the results that have occurred since the penultimate compilation to the last compilation are displayed.	: : Correct balance difference.
The last balance differences determined are corrected. The same text file is used for this as is used to compare the last results.	: Order parts
-	: : Incorrect "tradeAgreement"
Test looks for order parts where the slot "tradeAgreement" is not the main supplier.	: Attributes
-	:: Search attributes

Test searches for all attributes that have slots corresponding to other attributes.

Buttons	Button
Description	Close

The window is closed.

Results window

The results window shows the results of a test that was started from the inspection screen. From here, you can double-click to jump directly to the editing screen of the displayed object. Furthermore, the usual toolbar buttons such as document history, dispo account, etc. are available. Any document can be dropped into this window. This is interesting for cancellation or repair runs that are in the cockpit.

Toolbar	Icon
	tree.png
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	copytoclipboard.png

Copy analysis to clipboard

Fields	Field
Description	List

List of result entries

Buttons	Button
Description	Close

The window is closed.

Parts environment test window

The part environment test window provides further restriction options for the execution of the test run.

Toolbar	Icon
	CX_AMOUNT_calculation.png
	tree.png
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	copytoclipboard.png

Copy analysis to clipboard

Fields	Field
Description	Preselection
-	: part selection
-	: : Bearing parts only
Only bearing parts are considered in the test run	: : Part type
-	: : : All parts
All part types are considered	: : : Only variant parts
Only variant parts are taken into account	: : : Only sub-parts/single parts
Only sub-parts/single parts are taken into account	: : Processor
Selected employee	: : cost centre
Selected cost centre	: period
-	: : investment date part (from-to)
Either only a date such as "today", a period open into the future or past (-01.01.2005 or 01.01.2005-) or a fixed period (1.1.2005-1.7.2005) can be entered.	: : No precalculation since (date)
Only a current date is expected in the delimitation date for the preliminary part costing of production parts (01.01.2005). If a production part has not received a preliminary cost estimate since the specified date, it appears in the list. If no date has been entered in this field, the system generally only checks whether there has ever been a preliminary cost estimate for this part.	: Test mode
-	: : Execute test conditions
(see below under "Integrated Tests in the Part Environment Test").	: : Parts without operations
Only the test "Parts without operations" is executed.	: : Unconditional
	List

Buttons	Button
Description	Agent
Select employee	Cost centre
Select cost centre	Close

The window closes.

Integrated tests in the parts environment test::

• The test lists all parts...
• without logistics indicator
• without order or production role depending on the logistics indicator
• without staging type
• without SVP (if not variant part)
• with order role but without A-supplier
• with A-supplier but unsuitable lot size
• with production role but without preliminary costing (can be delimited by date field on selection screen! For more information see here below)
• with production role but without lot size
• with production role but with unsuitable lot size on material and labour cost tables
• with production role but without bill of material (but bill of material not mandatory if "dispos.assembly" = DB)
• with production role but without routing (but routing not mandatory if "constr.assembly" = KB)
  • Parts without operations
  • No sales role
  • Simple part has no bill of material or operations
  • For sub-parts -> the sub-part and variant part have no bill of material or operations

For variant part -> the variant part and all subparts have no BOM or operations.

... ... The list can be sorted and evaluated accordingly according to the desired data field (e.g. lot size error A supplier or BOM number)....

Check for bills of material and routings
Constructive assembly:

No routing needs to be present for constructive assemblies. The constructive assembly is not created as a gozzintoposition. It contains sub-parts that must already be contained in the superordinate routing, because that is where the gozzino items are moved to. However, they must contain a parts list.
Purely dispositive assembly:

For purely MRP assemblies, the system only checks for an existing routing if the logistics indicator of the part is set to "production part". A bill of material must not be present (otherwise it would not be a purely MRP assembly!).

• Pre-calculation in the part environment test
  • Date entered as delimitation date in the field "No preliminary costing since (date)":
    • A one appears in the column "VKK missing (=preliminary costing missing)" if...
    • no preliminary costing has been found for a production part since the date entered.
    • and the part is released
  • and the part is a stock part or an MRP part with stock on hand
    In the column "le.VKK-Transfer. (=last precalculation transfer by production role)" the date of the last transfer of a preliminary part calculation appears.
    On the production parts screen in the "Costs" tab, this date appears below the preliminary parts costing pointer.
    This date is only displayed in the list if a parts preliminary costing pointer exists.
• • No date entered as accrual date::
    • In the column "VKK missing (=pre-calculation missing)" a one appears if...
    • no preliminary cost estimate has ever been created for a production part
    • and the part is released
  • and the part is a stock item or an MRP item with stock on hand
    In the column "le.VKK-Transfer. (=last precalculation transfer by production role)" the date of the last transfer of a preliminary part calculation appears.
    On the production parts screen in the "Costs" tab, this date appears below the preliminary parts costing pointer.

This date is only displayed in the list if a parts preliminary costing pointer exists.

Number of parts

Fields	Field
Description	Number of all parts
Number of all parts	...variant parts
Number of variant parts	...subparts
Number of subparts	...individual parts
Number of individual parts	Purchased parts/manufactured parts
-	: dispositive
Number of dispositive parts	: not dispositive
Number of non-disposable parts	List

List of part roles and their number

Buttons	Button
Description	Close

The window is closed.

No logistics indicator

Toolbar	Symbol
	CX_AMOUNT_calculation.png
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	copytoclipboard.png

Copy analysis to clipboard

Fields	Field
Description	Preselection
-	: part selection
-	: : Valid parts only
Only valid parts are considered	: : Only approved parts
Only released parts are taken into account	: : Part type
-	: : : All parts
All part types are considered	: : : Only variant parts
Only variant parts are taken into account	: : : Only sub-parts/single parts
Only sub-parts/single parts are taken into account	: Period
-	: : investment date part (from-to)
Either only a date such as "today", a period open into the future or past (-01.01.2005 or 01.01.2005-) or a fixed period (1.1.2005-1.7.2005) can be entered.	List

Buttons	Button
Description	Close

The window is closed.

No part use
Parts that have a sales role are not considered in this test because the order items level 0 are not posted to the part usage. In addition, it may be normal that a level 0 production part does not appear in any other master parts list because it is sold directly.
When testing for existing movement data, movements of the sub-parts are also checked for variant parts, as it can happen that the variant part itself has never remained in a BOM, but has always been exploded into one of its sub-parts.
When testing for occurrences in other master BOMs, a check is also made for subparts to see whether their variant part occurs in a master BOM. Subparts are usually never in master BOMs, but always the variant part.

It would not necessarily be wrong for a variant part to have no part usages of its own - or for a sub-part to have no further master BOM occurrences of its own.

Toolbar	Symbol
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	copytoclipboard.png

Copy analysis to clipboard

Fields	Field
Description	List

Buttons	Button
Description	Close

The window is closed.

Invalid parts

Toolbar	Icon
	copytoclipboard.png

Copy analysis to clipboard

Fields	Field
Description	List

Buttons	Button
Description	Close

The window is closed.

Invalid parts in master parts lists

If parts are invalid and these are used in BOMs, these BOMs cannot be exploded when creating the part request. With this search run, all valid items of BOMs are checked whether an invalid part is used, if so, it is displayed.

You now have the option of editing the parts list items individually by hand - double-click - or simply transfer the validity from the part.

Toolbar	Symbol
	CX_AMOUNT_calculation.png
	copytoclipboard.png
	delete.png
	CX_VALIDITY.png

The validity from the part is transferred to the item, i.e. if the part was valid until 31.12.2013, the item is then also only valid until 31.12.2013. The validity of the items can also be carried out when setting the part validity. See

Invalid parts with valid storage locations

Toolbar	Icon
	copytoclipboard.png
	delete.png
	CX_STOCK_ACCOUNT.png
	CX_VALIDITY.png

Validity

Fields	Field
Description	List

Buttons	Button
Description	Close

The window is closed.

Wrong price table

Toolbar	Symbol
	CX_AMOUNT_calculation.png
	tree.png
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	copytoclipboard.png

Copy analysis to clipboard

Fields	Field
Description	Preselection
-	: Prices to be checked
-	: : Order roll price
	: : A supplier price
	: : B-supplier price
	: : C supplier price
	: parts selection
-	: : Bearing parts only
Only bearing parts are considered	: : Part type
-	: : : All parts
All part types are considered	: : : Only variant parts
Only variant parts are taken into account	: : : Only sub-parts/single parts
Only sub-parts/single parts are taken into account	: Period (investment date part)
	List

Buttons	Button
Description	Close

The window is closed.

Incorrectly registered work sequences

Toolbar	Icon
	CX_STOCK_ACCOUNT.png
	tree.png
	copytoclipboard.png
	delete.png

Remove selected entries from the dispo account of the workplaces.

Fields	Field
Description	List

Buttons	Button
Description	Close

The window is closed.

Not registered receipts

Toolbar	Icon
	copytoclipboard.png

Copy analysis to clipboard

Fields	Field
Description	List

Buttons	Button
Description	Close

The window is closed.

Differences warehouse statistics - storage bin accounts - warehouse account.

Differences between warehouse statistics and warehouse accounts can occur due to unfinished months of parts. In order to eliminate these differences, various test runs have been implemented.

Four steps are required to restore a completely synchronous picture:

First of all, it must be checked whether the month-end closing for parts in certain months was not carried out, or whether the final value is no longer correct due to postings that were only made after the month-end closing.

Instructions on how to adjust the differences between the warehouse statistics and the storage location accounts.

The very first thing to do is to start a test run that finds interrupted closing chains or closed months where a booking was still made after closing.

To do this, open the new cockpit and start this run Interrupted chain:

A result window appears:

Results window - Interrupted chain

Toolbar	Icon
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	copytoclipboard.png
	delete.png
	check_green.png

Correct data for selected entries

Fields	Field
Description
Missing degrees	: list
View of all months still changed after closure.
New parts to be completed	: list

Entry per part included indicating from when month-end closings must be redone to date.

Buttons	Button
Description	Close

The window is closed.

In this result window you can now see all the months that were still changed after completion.

In the second notebook tab, there is now only one entry per part with the indication from when the month-end closings have to be redone until today.

This list should now be sorted by month.

Then open the warehouse statistics and set the date as shown in the column for the part and up to the last closed period.

Now mark all parts in the result list that have to be newly completed as of January and simply drag and drop them into the warehouse statistics.

All months in this period are displayed (for all warehouses where this part was moved in this period).

Now in the warehouse statistics via the menu

"Closings->Repeat monthly closing" to repeat the monthly closing.

The list is empty after closing. It can be rebuilt via the button "Execute statistics" (not necessary, only if the result is to be checked).

Proceed in the same way with all parts in the list. Then the other three runs can be started one after the other and corrected if necessary.

Differences storage bin accounts

Toolbar	Symbol
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	delete.png
	check_green.png
	copytoclipboard.png

Copy analysis to clipboard

Fields	Field
Description	List

Buttons	Button
Description	Close

The window is closed.

Differences warehouse account

Toolbar	Icon
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	copytoclipboard.png

Copy analysis to clipboard

Fields	Field
Description	List

Buttons	Button
Description	Close

The window is closed.

Differences warehouse statistics

Matches the warehouse statistics with the warehouse accounts. It checks the "closing.quantity" of the last warehouse statistics with the warehouse stock, if this is not present the system calculates it. It does not have to be the last closed statistic, a new statistic is already opened when a part is booked in or booked out. It can only be changed in this statistic.

If differences have arisen in the warehouse statistics that were found here in this run, they can be corrected immediately in this window. For this purpose, the individual data are displayed in the list with the month to be corrected, as well as the current and the newly calculated quantities and values. So you already have an overview here of which sums account for the changes.

Buttons are provided in the toolbar for correcting or simply removing from the results list.

After the correction, the corresponding month does not need to be closed again, as the values of the closing are adjusted at the same time.

Toolbar	Icon
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	copytoclipboard.png
	delete.png
	check_green.png

Correct data for selected entries

Fields	Field
Description	List

Buttons	Button
Description	Close

The window is closed.

Storage bin accounts without inventory

Search window in which a date can be entered and warehouses selected. The system then searches either for all selected warehouses or, if none was selected, for all warehouses for which no inventory has been posted since the date entered. The evaluation can also be carried out via the business year. In this case, it is checked for all parts of the selected warehouses whether a stocktaking was posted in the selected business year. Parts that did not have any stock movements in the selected business year are ignored. The entries found are displayed in the lower list. From this list, the entries found can be dragged directly into an inventory using Drag&Drop.

The checkbox "Also invalid storage bins/parts" can be used to control whether the currently invalid parts or storage bins/parts are to be taken into account or not.

Toolbar	Symbol
	CX_AMOUNT_calculation.png
	CX_STOCK_on.png
	CX_STOCK_log.png
	CX_DISPO_ACCOUNT.png
	CX_STOCK_ACCOUNT.png
	copytoclipboard.png
	delete.png

Remove selected entries from list

Fields	Field
Description	Date
Date from which to check whether an inventory has been posted.	Financial year
Fiscal year in which it is to be checked whether an inventory was posted for the parts of the selected warehouses or all warehouses.	Also invalid storage bins/parts
If this tick is set, all invalid warehouses are also displayed for selection. The subsequent search then no longer excludes invalid storage bin accounts.	Warehouse list
Warehouses to be included in the search. If no warehouse is selected, all warehouses are searched.	Result list

All storage bin part accounts found

Buttons	Button
Description	OK

The search is executed and the results are returned to the calling window.

Number of parts lists

Various numbers of parts lists are displayed. The button can be used to list the group of BOMs found there.

Buttons	Button
Description	Close

The window is closed.

Number of routings

Various numbers of work plans are displayed. The button can be used to list the group of work plans found there.

Buttons	Button
Description	Close

The window is closed.

Spare part test window

Toolbar	Icon
	copytoclipboard.png
	delete.png

Remove selected entries from list

Implemented tests (fields and buttons)	Buttons
Description	Without offer+order
Spare parts without offer and order	Without identifier in SL
Spare parts that are in master BOMs without "spare part" identifier.	SL without spare part
BOM item with "spare part" identifier and without spare parts that are in master BOMs without "spare part" identifier.	Parts classes
Part classes containing spare parts	Specification
Spare parts containing duplicates in the specification table	Price history

Spare parts, price history for prices as value of quantity exported to file.

Sales item tests

Search for parts with different characteristics in relation to its sales part.

The following search functions are available :	Menu item
Description	Parts (variant or single parts) without sales item
Search for variant and single parts that do not have a sales role stored.	Parts with sales parts and without manufacturer
Search for variant and individual parts that have a sales, spare parts or special sales role, but no manufacturer is stored in the parts master.	Parts with several sales roles

Search for parts that have several sales-related roles, i.e. that have e.g. spare part and sales part roles.

Menu	Menu item
Description	Edit
-	: Change parts settings with Wizzard

You can change certain settings/values of the selected parts in one run. See

Toolbar	Icon
	copytoclipboard.png
	delete.png

Remove selected entries from list

• Related topics
• Index
• Inspection offers/orders

Inspection Accounting

---

• Technical documentation
• Implementation
• Quality assurance

Part master Testutilities module
To export objects of a collection or vector to a text file, there are the macros SaveCollectionToDisk and ReadCollectionFromDisk.

The macro SaveCollectionToDisk saves all database addresses of each object contained in the vector to a text file.

The call is made as follows::

Vector Filename SaveCollectionToDisk

The ReadCollectionFrom Disk macro returns the objects determined from the database addresses of the transferred file name in a vector as a return parameter:

File name ReadCollectionFromDisk -> Vector

Part root Testutlities Module

Module name

utilitem.mod

Classes

-

Security

In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.

Received messages	Message	Parameter	Function
Security

Sent messages	Message	Parameters	Function
Receive module